11/12/2024 22:07
As per instructions,
- The self trigger works but the trigger values are tricky since they don't correspond to the Y-axis. The HDSoC series of cards uses low and high reference values to set the lower and upper limit for the comparator circuit, then an 8-bit register controls the trigger values between the limits.
To help users we added the Threshold scanner, to map the signal values to the trigger values.i
It will step through a range of trigger values and ask the ASIC how many times it triggers then create a plot with x-axis: trigger_value and y-axis: times triggered:
The peak shows the trigger value for the noise and the actual position depends on the external bias value and the individual channel. A good starting point is low_ref: 6 and high_ref: 12, with 0-255 in steps of 1.
The time it takes to scan scales linearly with the number of channels since the internal counter needs time to reset, it's a good idea to start with one channel.The peak is only slightly temperature dependent and will only move a few points over time, you can re-use the result in the future, or use them to guide you for future scans.
The external trigger input should work now, it's an LVCMOS25 input and accepts pulses 0-2.5V with a width of 10-100ns.
Let me know if you want more clarification!
Cheers,
Marcus Luck
Lead Software EngineerNalu Scientific LLC
First I followed these instructions for just channel 0, but had no luck.
Then I followed these instructions, and was able to produce a trigger plot for channels 0, 1, 16, and 17:
low threshold 6, high threshold 12
I scanned with low threshold 6 and high threshold 12. I scanned 0-255 in this range at first but then switched to 60-80 for a better plot. I also tried shortening the low threshold to 8 and high threshold to 9. I still saw the signal, but to my surpise it wasn't wider.
low threshold 8, high threshold 9
I must not be understanding what the thresholds did. I though they effectively define the range of the comparator, and the scan divides that range up further in 256 parts. So by that logic making the threshold 6 times smaller (12 - 6 = 6 to 9 - 8 = 1) should make the signal 6 times wider.
Even worse, I wasn't able to trigger on these settings using the naluscope. I was just setting the thresholds and values shown on the graph in the trigger settings then starting an acquisiton. I tried varying the thresholds a lot, but with no luck, I was not able to trigger on a single noise trace.
12/12/2024 22:10
Earlier I tried running the 2 crate system, but i could not connect to the digitizers in the second crate. I could still talk to the MCH and AMC13 however. So I went to the lab and noticed the crate looked like this
Immediately you notice the blue lights on the WFD5s that indicate they're disabled. There's also the red critical light on the crate itself.
I first tried restarting the WFD5s by pulling out the tab and putting it back in. That worked for about 20 seconds before they went back to their disabled state.
I then tried power cycling that crate. After about 2 minutes the crate's red "crit" light goes on first, then a few seconds after both the WFD5s disable themselves. The AMC13 and MCH still seem to work fine. We don't have this problem with crate one.
I don't know how to debug this, though I'm almost certain it's a crate issue.
12/12/2024 22:53
I tried doing another threshold scan today. This time it worked.
Threshold scan for channel 0 low ref 6 high ref 12
I did exactly as I did before, setting the triggers to where the threshold scan peaked with the same high and low ref. This time I was able to trigger on noise.
The difference was ALL other channels had to be set to zero threshold (before I had them set to 1)
13/12/2024 14:04
Taking the WFD5s out of the crate and leaving it on seemed to get rid of the "cirtical" warning. I have left it up for about 30 minutes with no error.
Also, I found the correct fru print command:
[root@dhcp-10-163-105-238 ~]# ipmitool -H 192.168.2.15 fru print Password: Activate Session command failed Error: Unable to establish LAN session Error: Unable to establish IPMI v1.5 / RMCP session [root@dhcp-10-163-105-238 ~]# ipmitool -H 192.168.2.15 -U 'shelf' -P 'shelf' fru print FRU Device Description : Builtin FRU Device (ID 0) Board Mfg Date : Tue May 14 12:51:00 2024 Board Mfg : VadaTech Board Product : ShMC Board Serial : na Board Part Number : VTUTCSH Product Manufacturer : VadaTech Product Name : ShMC Product Part Number : VTUTCSH Product Version : n/a Product Serial : na Product Extra : 5D32 FRU Device Description : SHELF FRU INFO (ID 254) Chassis Type : Other Chassis Part Number : VT892 Chassis Serial : 1940394 Board Mfg Date : Sun Apr 5 08:09:00 2015 Board Mfg : VadaTech Board Product : UTCA Shelf Board Serial : 1940394 Board Part Number : VTSH INFO Product Manufacturer : VadaTech Product Name : UTCA Shelf Product Part Number : VTSH INFO Product Version : 3.2.0 Product Serial : 1940394 Product Extra : 5D32 FRU Device Description : UTCA CARRIER (ID 0) Unsupported device FRU Device Description : UTCA CARRIER Board Mfg Date : Tue May 14 12:51:00 2024 Board Mfg : VadaTech Board Product : UTCC Board Serial : na Board Part Number : VTUTCC Product Manufacturer : VadaTech Product Name : UTCC Product Part Number : VTUTCC Product Version : 7.5.0 Product Serial : na Product Extra : 5D32 FRU Device Description : SH FRU DEV1 (ID 1) Chassis Type : Other Chassis Part Number : VT892 Chassis Serial : 1940394 Board Mfg Date : Sun Apr 5 08:09:00 2015 Board Mfg : VadaTech Board Product : UTCA Shelf Board Serial : 1940394 Board Part Number : VTSH INFO Product Manufacturer : VadaTech Product Name : UTCA Shelf Product Part Number : VTSH INFO Product Version : 3.2.0 Product Serial : 1940394 Product Extra : 5D32 FRU Device Description : UTCA MCH (ID 3) Unsupported device FRU Device Description : VT VT095 (ID 40) Unsupported device FRU Device Description : VT VT095 (ID 41) Unsupported device FRU Device Description : VT UTC020 (ID 50) Unsupported device FRU Device Description : MCH DA INFO (ID 80) Board Mfg Date : Thu Jul 27 10:14:00 2017 Board Mfg : VadaTech Board Product : DA-None Board Part Number : 0000 Product Manufacturer : VadaTech Product Name : DA-None Product Version : 1.0.0
[root@dhcp-10-163-105-238 ~]# ipmitool -H 192.168.2.15 fru print
Password:
Activate Session command failed
Error: Unable to establish LAN session
Error: Unable to establish IPMI v1.5 / RMCP session
[root@dhcp-10-163-105-238 ~]# ipmitool -H 192.168.2.15 -U 'shelf' -P 'shelf' fru print
FRU Device Description : Builtin FRU Device (ID 0)
Board Mfg Date : Tue May 14 12:51:00 2024
Board Mfg : VadaTech
Board Product : ShMC
Board Serial : na
Board Part Number : VTUTCSH
Product Manufacturer : VadaTech
Product Name : ShMC
Product Part Number : VTUTCSH
Product Version : n/a
Product Serial : na
Product Extra : 5D32
FRU Device Description : SHELF FRU INFO (ID 254)
Chassis Type : Other
Chassis Part Number : VT892
Chassis Serial : 1940394
Board Mfg Date : Sun Apr 5 08:09:00 2015
Board Mfg : VadaTech
Board Product : UTCA Shelf
Board Serial : 1940394
Board Part Number : VTSH INFO
Product Manufacturer : VadaTech
Product Name : UTCA Shelf
Product Part Number : VTSH INFO
Product Version : 3.2.0
Product Serial : 1940394
Product Extra : 5D32
FRU Device Description : UTCA CARRIER (ID 0)
Unsupported device
FRU Device Description : UTCA CARRIER
Board Mfg Date : Tue May 14 12:51:00 2024
Board Mfg : VadaTech
Board Product : UTCC
Board Serial : na
Board Part Number : VTUTCC
Product Manufacturer : VadaTech
Product Name : UTCC
Product Part Number : VTUTCC
Product Version : 7.5.0
Product Serial : na
Product Extra : 5D32
FRU Device Description : SH FRU DEV1 (ID 1)
Chassis Type : Other
Chassis Part Number : VT892
Chassis Serial : 1940394
Board Mfg Date : Sun Apr 5 08:09:00 2015
Board Mfg : VadaTech
Board Product : UTCA Shelf
Board Serial : 1940394
Board Part Number : VTSH INFO
Product Manufacturer : VadaTech
Product Name : UTCA Shelf
Product Part Number : VTSH INFO
Product Version : 3.2.0
Product Serial : 1940394
Product Extra : 5D32
FRU Device Description : UTCA MCH (ID 3)
Unsupported device
FRU Device Description : VT VT095 (ID 40)
Unsupported device
FRU Device Description : VT VT095 (ID 41)
Unsupported device
FRU Device Description : VT UTC020 (ID 50)
Unsupported device
FRU Device Description : MCH DA INFO (ID 80)
Board Mfg Date : Thu Jul 27 10:14:00 2017
Board Mfg : VadaTech
Board Product : DA-None
Board Part Number : 0000
Product Manufacturer : VadaTech
Product Name : DA-None
Product Version : 1.0.013/12/2024 14:11
Putting just one of the WFD5s back into slot 3 causes the same issue as before. This is the case with either of the digitizers (i.e. putting just the WFD5 that was previously in slot 5 into slot 3 or putting the WFD5 that was previous in slot 3 into slot 3). Here's the fru print:
[root@dhcp-10-163-105-238 ~]# ipmitool -H 192.168.2.15 -U 'shelf' -P 'shelf' fru print FRU Device Description : Builtin FRU Device (ID 0) Board Mfg Date : Tue May 14 12:51:00 2024 Board Mfg : VadaTech Board Product : ShMC Board Serial : na Board Part Number : VTUTCSH Product Manufacturer : VadaTech Product Name : ShMC Product Part Number : VTUTCSH Product Version : n/a Product Serial : na Product Extra : 5D32 FRU Device Description : SHELF FRU INFO (ID 254) Chassis Type : Other Chassis Part Number : VT892 Chassis Serial : 1940394 Board Mfg Date : Sun Apr 5 08:09:00 2015 Board Mfg : VadaTech Board Product : UTCA Shelf Board Serial : 1940394 Board Part Number : VTSH INFO Product Manufacturer : VadaTech Product Name : UTCA Shelf Product Part Number : VTSH INFO Product Version : 3.2.0 Product Serial : 1940394 Product Extra : 5D32 FRU Device Description : UTCA CARRIER (ID 0) Unsupported device FRU Device Description : UTCA CARRIER Board Mfg Date : Tue May 14 12:51:00 2024 Board Mfg : VadaTech Board Product : UTCC Board Serial : na Board Part Number : VTUTCC Product Manufacturer : VadaTech Product Name : UTCC Product Part Number : VTUTCC Product Version : 7.5.0 Product Serial : na Product Extra : 5D32 FRU Device Description : SH FRU DEV1 (ID 1) Chassis Type : Other Chassis Part Number : VT892 Chassis Serial : 1940394 Board Mfg Date : Sun Apr 5 08:09:00 2015 Board Mfg : VadaTech Board Product : UTCA Shelf Board Serial : 1940394 Board Part Number : VTSH INFO Product Manufacturer : VadaTech Product Name : UTCA Shelf Product Part Number : VTSH INFO Product Version : 3.2.0 Product Serial : 1940394 Product Extra : 5D32 FRU Device Description : UTCA MCH (ID 3) Unsupported device FRU Device Description : CU WFD5 (ID 7) Unsupported device FRU Device Description : VT VT095 (ID 40) Unsupported device FRU Device Description : VT VT095 (ID 41) Unsupported device FRU Device Description : VT UTC020 (ID 50) Unsupported device FRU Device Description : MCH DA INFO (ID 80) Board Mfg Date : Thu Jul 27 10:14:00 2017 Board Mfg : VadaTech Board Product : DA-None Board Part Number : 0000 Product Manufacturer : VadaTech Product Name : DA-None Product Version : 1.0.0 [root@dhcp-10-163-105-238 ~]# ping 192.168.2.3 PING 192.168.2.3 (192.168.2.3) 56(84) bytes of data. ^C --- 192.168.2.3 ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 1023ms [root@dhcp-10-163-105-238 ~]#
[root@dhcp-10-163-105-238 ~]# ipmitool -H 192.168.2.15 -U 'shelf' -P 'shelf' fru print
FRU Device Description : Builtin FRU Device (ID 0)
Board Mfg Date : Tue May 14 12:51:00 2024
Board Mfg : VadaTech
Board Product : ShMC
Board Serial : na
Board Part Number : VTUTCSH
Product Manufacturer : VadaTech
Product Name : ShMC
Product Part Number : VTUTCSH
Product Version : n/a
Product Serial : na
Product Extra : 5D32
FRU Device Description : SHELF FRU INFO (ID 254)
Chassis Type : Other
Chassis Part Number : VT892
Chassis Serial : 1940394
Board Mfg Date : Sun Apr 5 08:09:00 2015
Board Mfg : VadaTech
Board Product : UTCA Shelf
Board Serial : 1940394
Board Part Number : VTSH INFO
Product Manufacturer : VadaTech
Product Name : UTCA Shelf
Product Part Number : VTSH INFO
Product Version : 3.2.0
Product Serial : 1940394
Product Extra : 5D32
FRU Device Description : UTCA CARRIER (ID 0)
Unsupported device
FRU Device Description : UTCA CARRIER
Board Mfg Date : Tue May 14 12:51:00 2024
Board Mfg : VadaTech
Board Product : UTCC
Board Serial : na
Board Part Number : VTUTCC
Product Manufacturer : VadaTech
Product Name : UTCC
Product Part Number : VTUTCC
Product Version : 7.5.0
Product Serial : na
Product Extra : 5D32
FRU Device Description : SH FRU DEV1 (ID 1)
Chassis Type : Other
Chassis Part Number : VT892
Chassis Serial : 1940394
Board Mfg Date : Sun Apr 5 08:09:00 2015
Board Mfg : VadaTech
Board Product : UTCA Shelf
Board Serial : 1940394
Board Part Number : VTSH INFO
Product Manufacturer : VadaTech
Product Name : UTCA Shelf
Product Part Number : VTSH INFO
Product Version : 3.2.0
Product Serial : 1940394
Product Extra : 5D32
FRU Device Description : UTCA MCH (ID 3)
Unsupported device
FRU Device Description : CU WFD5 (ID 7)
Unsupported device
FRU Device Description : VT VT095 (ID 40)
Unsupported device
FRU Device Description : VT VT095 (ID 41)
Unsupported device
FRU Device Description : VT UTC020 (ID 50)
Unsupported device
FRU Device Description : MCH DA INFO (ID 80)
Board Mfg Date : Thu Jul 27 10:14:00 2017
Board Mfg : VadaTech
Board Product : DA-None
Board Part Number : 0000
Product Manufacturer : VadaTech
Product Name : DA-None
Product Version : 1.0.0
[root@dhcp-10-163-105-238 ~]# ping 192.168.2.3
PING 192.168.2.3 (192.168.2.3) 56(84) bytes of data.
^C
--- 192.168.2.3 ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1023ms
[root@dhcp-10-163-105-238 ~]#commands like read_status fail because IP connection is down, i.e. you cannot ping the WFD5s
[root@dhcp-10-163-105-238 software]# python read_status.py 2 3
Crate 02, Slot 03
Traceback (most recent call last):
File "/home/pioneer/packages/wfdConfig/software/read_status.py", line 55, in <module>
wfd.dispatch()
uhal._core.UdpTimeout: Timeout (1000 milliseconds) occurred for UDP receive from target with URI: ipbusudp-2.0://192.168.2.3:50001
[root@dhcp-10-163-105-238 software]# python read_status.py 2 5
Crate 02, Slot 05
Traceback (most recent call last):
File "/home/pioneer/packages/wfdConfig/software/read_status.py", line 55, in <module>
wfd.dispatch()
uhal._core.UdpTimeout: Timeout (1000 milliseconds) occurred for UDP receive from target with URI: ipbusudp-2.0://192.168.2.5:50001
[root@dhcp-10-163-105-238 software]#[root@dhcp-10-163-105-238 software]# python read_status.py 2 3
Crate 02, Slot 03
Traceback (most recent call last):
File "/home/pioneer/packages/wfdConfig/software/read_status.py", line 55, in <module>
wfd.dispatch()
uhal._core.UdpTimeout: Timeout (1000 milliseconds) occurred for UDP receive from target with URI: ipbusudp-2.0://192.168.2.3:50001
[root@dhcp-10-163-105-238 software]# python read_status.py 2 5
Crate 02, Slot 05
Traceback (most recent call last):
File "/home/pioneer/packages/wfdConfig/software/read_status.py", line 55, in <module>
wfd.dispatch()
uhal._core.UdpTimeout: Timeout (1000 milliseconds) occurred for UDP receive from target with URI: ipbusudp-2.0://192.168.2.5:50001
[root@dhcp-10-163-105-238 software]#13/12/2024 14:25
I swapped out the WFD5 that was in slot 11 of crate 1 with the WFD5 that was in slot 3 of crate 2. Now there is just a WFD5 that we know is working in slot 3 of crate 2 and no other WFD5. This causes the same "critical error", indicating it is not a problem with the digitizer itself but a combination of the crate and digitizers.
13/12/2024 14:36
I tried moving the WFD5 that was working in crate 1 slot 11 to crate 2 slot 9 now. The issue still persists.